Sometimes, when GitHub has troubles, it doesn't deliver webhook events to integrations (including GHA CI). In this case, closing+reopening the PR when GH outage is over, triggers it and other automations properly.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.22%. Comparing base (2b6bb4b) to head (fe5d064).
⚠️ Report is 5 commits behind head on 3.14.
✅ All tests successful. No failed tests found.

@@           Coverage Diff           @@
##             3.14   #11991   +/-   ##
=======================================
  Coverage   98.22%   98.22%           
=======================================
  Files         128      128           
  Lines       44990    44990           
  Branches     2434     2434           
=======================================
+ Hits        44190    44192    +2     
+ Misses        618      615    -3     
- Partials      182      183    +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Merging this PR will not alter performance

✅ 59 untouched benchmarks

_{Comparing rodrigobnogueira:backport/11737-to-3.14 (fe5d064) with 3.14 (2b6bb4b)¹}

Sometimes, when GitHub has troubles, it doesn't deliver webhook events to integrations (including GHA CI). In this case, closing+reopening the PR when GH outage is over, triggers it and other automations properly.

FYI, I'm finding that increasingly rare these days. Most of the time now it's just because there's no runners available or the previous commit's workflow is still cancelling, and it then works once it's caught up.

Yeah, it depends. But sometimes GH disables webhook deliveries at the time of big outages manually. They the re-enable them once they fixed things. But they never retroactively deliver those events that happened during that period.

This was mostly an educational comment for Rodrigo, though, since he tried achieving the same by pushing empty commits.